Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a807f8cc8cbbc95198b425d694cfec891b9152745b24f923156b2993b023ec

Tx prefix hash: 82861f08e984304ce5643e6d2908c6c4a1b0a39a2dfa3a969a64344e927d73f5
Tx public key: d3bfe1e829023b0e58959d3b583250f023be3b4bdc06f43949c44fdd61b714d3
Timestamp: 1725903969 Timestamp [UCT]: 2024-09-09 17:46:09 Age [y:d:h:m:s]: 00:167:05:02:34
Block: 1106501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119309 RingCT/type: yes/0
Extra: 01d3bfe1e829023b0e58959d3b583250f023be3b4bdc06f43949c44fdd61b714d3021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d4c691c0a02e2d8615c8589813756d8fb666c06441f2864acb4a363df479e0b 0.600000000000 1584100 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": 1106511, "vin": [ { "gen": { "height": 1106501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d4c691c0a02e2d8615c8589813756d8fb666c06441f2864acb4a363df479e0b" } } ], "extra": [ 1, 211, 191, 225, 232, 41, 2, 59, 14, 88, 149, 157, 59, 88, 50, 80, 240, 35, 190, 59, 75, 220, 6, 244, 57, 73, 196, 79, 221, 97, 183, 20, 211, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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