Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d32eb2ff366609d448ca9f7787578d8bf3ea3c3e7f9a34d9db26b8d40a6b45

Tx prefix hash: 5318622a9b13ec8c7a9858bdb264632f77548977e3e079be6e1cbe8df553822b
Tx public key: 73521b82025ffa71b226ce99f76707a1a615ad6f5d58a5e1dbb4ed19c00db109
Timestamp: 1754466163 Timestamp [UCT]: 2025-08-06 07:42:43 Age [y:d:h:m:s]: 00:143:04:48:56
Block: 1341323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101406 RingCT/type: yes/0
Extra: 0173521b82025ffa71b226ce99f76707a1a615ad6f5d58a5e1dbb4ed19c00db10902110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a17f4001c12150b228d04b0098baca300d3da3c9f3fec942fd6f5818e5dff4 0.600000000000 1829146 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": 1341333, "vin": [ { "gen": { "height": 1341323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a17f4001c12150b228d04b0098baca300d3da3c9f3fec942fd6f5818e5dff4" } } ], "extra": [ 1, 115, 82, 27, 130, 2, 95, 250, 113, 178, 38, 206, 153, 247, 103, 7, 161, 166, 21, 173, 111, 93, 88, 165, 225, 219, 180, 237, 25, 192, 13, 177, 9, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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