Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a4051ef72716d52d017160ebbf5e9076e9a20e36e9c868f74f9abbb80d5961d

Tx prefix hash: 1e5fe648c36a8f7b004cddbed09d62992a6aa2e42dc31c1b9009cd0a494117b3
Tx public key: 2c0dfb09cb186dbff0c5fc0dcec679f8e1c493d0a41a61c844fb7141f08f1bfa
Timestamp: 1718965364 Timestamp [UCT]: 2024-06-21 10:22:44 Age [y:d:h:m:s]: 00:314:02:39:23
Block: 1048957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224492 RingCT/type: yes/0
Extra: 012c0dfb09cb186dbff0c5fc0dcec679f8e1c493d0a41a61c844fb7141f08f1bfa0211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee3c9a008efcb507a849f625aff1e5b2c34e21622841b1c6148858fd4b152b1 0.600000000000 1519054 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": 1048967, "vin": [ { "gen": { "height": 1048957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee3c9a008efcb507a849f625aff1e5b2c34e21622841b1c6148858fd4b152b1" } } ], "extra": [ 1, 44, 13, 251, 9, 203, 24, 109, 191, 240, 197, 252, 13, 206, 198, 121, 248, 225, 196, 147, 208, 164, 26, 97, 200, 68, 251, 113, 65, 240, 143, 27, 250, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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