Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a34baf74cb0ca7ee8001e5635f5e81a9dfb5c4a1f9d7fd2736472d33641654

Tx prefix hash: 9a818fec0b2df76ad6f15e15f2478e3e44671d0c1b9c05d19a932bfa757dba57
Tx public key: 53779d01b345c4cee67b72f2f52e2f953d8228c11313d1f7e9dcbfa68cf0c092
Timestamp: 1711758740 Timestamp [UCT]: 2024-03-30 00:32:20 Age [y:d:h:m:s]: 01:235:23:50:37
Block: 989250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427331 RingCT/type: yes/0
Extra: 0153779d01b345c4cee67b72f2f52e2f953d8228c11313d1f7e9dcbfa68cf0c0920211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f831bce8bd764f71cb1d1cff59e9200bc06bfeabd52a877e4da8464fe7190295 0.600000000000 1449545 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": 989260, "vin": [ { "gen": { "height": 989250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f831bce8bd764f71cb1d1cff59e9200bc06bfeabd52a877e4da8464fe7190295" } } ], "extra": [ 1, 83, 119, 157, 1, 179, 69, 196, 206, 230, 123, 114, 242, 245, 46, 47, 149, 61, 130, 40, 193, 19, 19, 209, 247, 233, 220, 191, 166, 140, 240, 192, 146, 2, 17, 0, 0, 0, 1, 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