Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64ecefcafb9ee8568f675a745afe7992fd8bb0568e7f1cda1330fb7063c1ea9

Tx prefix hash: 566f503fadc96bf212b6c90b7f04bc76673eb189c699cf2e5da0231f7bf9506f
Tx public key: 8c754bc11622060a0dd1717067bcd43c0f003fef523f18df69ba3d475af1f889
Timestamp: 1629125480 Timestamp [UCT]: 2021-08-16 14:51:20 Age [y:d:h:m:s]: 03:050:11:32:35
Block: 315384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 809279 RingCT/type: yes/0
Extra: 018c754bc11622060a0dd1717067bcd43c0f003fef523f18df69ba3d475af1f88902110000001706faf294000000000000000000

1 output(s) for total of 55.335310832000 dcy

stealth address amount amount idx
00: 06d6f37ed0641061431d16d60eadc9df1bde4412fada917d355e90e1c2a79bf3 55.335310832000 656413 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": 315394, "vin": [ { "gen": { "height": 315384 } } ], "vout": [ { "amount": 55335310832, "target": { "key": "06d6f37ed0641061431d16d60eadc9df1bde4412fada917d355e90e1c2a79bf3" } } ], "extra": [ 1, 140, 117, 75, 193, 22, 34, 6, 10, 13, 209, 113, 112, 103, 188, 212, 60, 15, 0, 63, 239, 82, 63, 24, 223, 105, 186, 61, 71, 90, 241, 248, 137, 2, 17, 0, 0, 0, 23, 6, 250, 242, 148, 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