Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd8d272af6e1d8f916f42a6dfb7127abf911b0734f64f10fae27ae78ded0ac4

Tx prefix hash: d6245cd53757641dc9812a099d6370f40403f952ec852eeaede60d9fc0b9184f
Tx public key: 544fb2a1a88f03933a604e58986ed9653db63a76e4fc1cc2e33bb21a1f6c58ab
Timestamp: 1716943884 Timestamp [UCT]: 2024-05-29 00:51:24 Age [y:d:h:m:s]: 00:240:05:52:56
Block: 1032222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171892 RingCT/type: yes/0
Extra: 01544fb2a1a88f03933a604e58986ed9653db63a76e4fc1cc2e33bb21a1f6c58ab0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07188ed69c56b1d31d15372506690dcce02e45b534339ac0f02bbd71a5b8c9af 0.600000000000 1500671 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": 1032232, "vin": [ { "gen": { "height": 1032222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07188ed69c56b1d31d15372506690dcce02e45b534339ac0f02bbd71a5b8c9af" } } ], "extra": [ 1, 84, 79, 178, 161, 168, 143, 3, 147, 58, 96, 78, 88, 152, 110, 217, 101, 61, 182, 58, 118, 228, 252, 28, 194, 227, 59, 178, 26, 31, 108, 88, 171, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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