Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f472be23b9bfb74028673828c34c207038f0a9edebb96772e000306e84f8fa7

Tx prefix hash: 4d49124f941e48b2fb4524c77158031425f18d61b240061749720a19c0626789
Tx public key: 82b3d3eae7a07cfea4103d83fae1cf2b6429263ccdf5e63a534f076c8d0c214d
Timestamp: 1712605585 Timestamp [UCT]: 2024-04-08 19:46:25 Age [y:d:h:m:s]: 00:291:03:17:39
Block: 996223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208371 RingCT/type: yes/0
Extra: 0182b3d3eae7a07cfea4103d83fae1cf2b6429263ccdf5e63a534f076c8d0c214d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c335588c50f88c6af9196cdc85780ba4147df693f09b282290cf380d772ef8b 0.600000000000 1456639 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": 996233, "vin": [ { "gen": { "height": 996223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c335588c50f88c6af9196cdc85780ba4147df693f09b282290cf380d772ef8b" } } ], "extra": [ 1, 130, 179, 211, 234, 231, 160, 124, 254, 164, 16, 61, 131, 250, 225, 207, 43, 100, 41, 38, 60, 205, 245, 230, 58, 83, 79, 7, 108, 141, 12, 33, 77, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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