Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 31fb74be6c58b317792c74993c187da1ddcfb81c1ad4c64b077d082bf5e994c0

Tx prefix hash: 20e1e1b4288e17cf7f2ecc15de9049a585ce2de9f9cb1eaf66dbffb6fdf14a8e
Tx public key: 63130b5ec363d0bfae9b3db720cc3e83cfb9d2fa7f2ab3ce3efa7c41e975132f
Timestamp: 1713883080 Timestamp [UCT]: 2024-04-23 14:38:00 Age [y:d:h:m:s]: 00:205:12:23:59
Block: 1006847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147103 RingCT/type: yes/0
Extra: 0163130b5ec363d0bfae9b3db720cc3e83cfb9d2fa7f2ab3ce3efa7c41e975132f0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8b9b24add874bb7a748b67c7d81fda2c7ecad9633472ae1ddbea89397a6e66b 0.600000000000 1467999 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1006857, "vin": [ { "gen": { "height": 1006847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8b9b24add874bb7a748b67c7d81fda2c7ecad9633472ae1ddbea89397a6e66b" } } ], "extra": [ 1, 99, 19, 11, 94, 195, 99, 208, 191, 174, 155, 61, 183, 32, 204, 62, 131, 207, 185, 210, 250, 127, 42, 179, 206, 62, 250, 124, 65, 233, 117, 19, 47, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8