Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00a172a24dba19a25b3ce715fd338af21d34061d05da27ec0462f9dc90d48c5b

Tx prefix hash: 66bb1fae9acab9598a44458b26bd43454f536bdbd2aa69280aff9b05d3574fae
Tx public key: 2340f5829da3a7a8df4c54d30672d8a64f1784c481203b9b7629529226e95c97
Timestamp: 1737357256 Timestamp [UCT]: 2025-01-20 07:14:16 Age [y:d:h:m:s]: 00:295:12:43:04
Block: 1201253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208766 RingCT/type: yes/0
Extra: 012340f5829da3a7a8df4c54d30672d8a64f1784c481203b9b7629529226e95c970211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb09da911e2f3633a9f88e893e80632d3639183d6a8e47b39a6a3f7f71c0f211 0.600000000000 1687902 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": 1201263, "vin": [ { "gen": { "height": 1201253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb09da911e2f3633a9f88e893e80632d3639183d6a8e47b39a6a3f7f71c0f211" } } ], "extra": [ 1, 35, 64, 245, 130, 157, 163, 167, 168, 223, 76, 84, 211, 6, 114, 216, 166, 79, 23, 132, 196, 129, 32, 59, 155, 118, 41, 82, 146, 38, 233, 92, 151, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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