Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a4f3cc5fd4db830c7e0e3c48e71fed08b8919bc3a3d0cf99bcf2ca4fa80195

Tx prefix hash: 4a0d269e26eff7bd174c08304e5abb2ae35b4031d58b1e0d39e77eaddbaf0deb
Tx public key: 83d0b661640379f9ac41b2c03ffa63fc3f7464350afe9023d7e33a965565b5d8
Timestamp: 1741219032 Timestamp [UCT]: 2025-03-05 23:57:12 Age [y:d:h:m:s]: 00:321:04:34:06
Block: 1233009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227241 RingCT/type: yes/0
Extra: 0183d0b661640379f9ac41b2c03ffa63fc3f7464350afe9023d7e33a965565b5d8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08d2fccf4ced2f04a71f163f9a43f41e54e1bc3f5da15d2b502e43c4994a4f01 0.600000000000 1719926 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": 1233019, "vin": [ { "gen": { "height": 1233009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08d2fccf4ced2f04a71f163f9a43f41e54e1bc3f5da15d2b502e43c4994a4f01" } } ], "extra": [ 1, 131, 208, 182, 97, 100, 3, 121, 249, 172, 65, 178, 192, 63, 250, 99, 252, 63, 116, 100, 53, 10, 254, 144, 35, 215, 227, 58, 150, 85, 101, 181, 216, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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