Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df3be7a243fa05c477b54cdd36ef1397758d814a270f04d194f16adf994d5f70

Tx prefix hash: 41f4ba4efe3e7b7dfabe54ec03128518696b481dc043be644fda606ba4aef23a
Tx public key: fcb0fbdefdb12c6847d3bbe252845680de61b6d3f1e89c49f46f8d27bad03b68
Timestamp: 1766124721 Timestamp [UCT]: 2025-12-19 06:12:01 Age [y:d:h:m:s]: 00:002:06:51:49
Block: 1436814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1638 RingCT/type: yes/0
Extra: 01fcb0fbdefdb12c6847d3bbe252845680de61b6d3f1e89c49f46f8d27bad03b680211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dabf88ea25ff1d6cbf1cb890141ab4a1226ec1b9b7f1f4c2035dfc3d645db12 0.600000000000 1925619 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": 1436824, "vin": [ { "gen": { "height": 1436814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dabf88ea25ff1d6cbf1cb890141ab4a1226ec1b9b7f1f4c2035dfc3d645db12" } } ], "extra": [ 1, 252, 176, 251, 222, 253, 177, 44, 104, 71, 211, 187, 226, 82, 132, 86, 128, 222, 97, 182, 211, 241, 232, 156, 73, 244, 111, 141, 39, 186, 208, 59, 104, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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