Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb7b370d72f2690eb3488933b96491352f30c2d1ecb7e886a7ed61b4e3327cd9

Tx prefix hash: 8f40dddee90810a0cbdc111260e0ac900c567f3c4427d0b93b6160a1a3bc9c26
Tx public key: 6f9bd23f6e12e0b2d54d3809f990e831d106fea1a96bfdaf787e2fbefbdfa10e
Timestamp: 1739048583 Timestamp [UCT]: 2025-02-08 21:03:03 Age [y:d:h:m:s]: 00:286:02:09:12
Block: 1215044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202224 RingCT/type: yes/0
Extra: 016f9bd23f6e12e0b2d54d3809f990e831d106fea1a96bfdaf787e2fbefbdfa10e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7007b681e66c2079de1b74fda3976f9320f7164c0faf0ec3133211b145ad0210 0.600000000000 1701841 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": 1215054, "vin": [ { "gen": { "height": 1215044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7007b681e66c2079de1b74fda3976f9320f7164c0faf0ec3133211b145ad0210" } } ], "extra": [ 1, 111, 155, 210, 63, 110, 18, 224, 178, 213, 77, 56, 9, 249, 144, 232, 49, 209, 6, 254, 161, 169, 107, 253, 175, 120, 126, 47, 190, 251, 223, 161, 14, 2, 17, 0, 0, 0, 2, 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