Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbc82f7866bfe7b6dff288e9b6b84c0154818583df3ccec9e7270fe8c7d2a572

Tx prefix hash: 5969262d4956fd980d7ddb50ab12ffa639c6a61dc9ef5ab5e7603ed8873300e5
Tx public key: d006a676fa3aab93d5fcd581b29ab2a4fc95bb495019dc72a282c986c6049290
Timestamp: 1698347946 Timestamp [UCT]: 2023-10-26 19:19:06 Age [y:d:h:m:s]: 01:173:10:44:47
Block: 878268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384965 RingCT/type: yes/0
Extra: 01d006a676fa3aab93d5fcd581b29ab2a4fc95bb495019dc72a282c986c6049290021100000006faf35c9c000000000000000000

1 output(s) for total of 0.754976693000 dcy

stealth address amount amount idx
00: dcd7cf2f10cfd289553f8fdc9bc30e94d6db51c6dc8f88644ff035afe8837d1a 0.754976693000 1333698 of 0

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": 878278, "vin": [ { "gen": { "height": 878268 } } ], "vout": [ { "amount": 754976693, "target": { "key": "dcd7cf2f10cfd289553f8fdc9bc30e94d6db51c6dc8f88644ff035afe8837d1a" } } ], "extra": [ 1, 208, 6, 166, 118, 250, 58, 171, 147, 213, 252, 213, 129, 178, 154, 178, 164, 252, 149, 187, 73, 80, 25, 220, 114, 162, 130, 201, 134, 198, 4, 146, 144, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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