Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 397debd71f130e2737a596fafc09812c92837917cc574800484d7acf1ee5ff63

Tx prefix hash: 58cb5496e0eb3cf2eccdf8af246067114c2045e1cf308ad5aa67f80ac753ea4c
Tx public key: f5812186f6ea5776c446e1c23bc71fb0f15bdc1a6775edd13bcd0dbd884dceea
Timestamp: 1694230413 Timestamp [UCT]: 2023-09-09 03:33:33 Age [y:d:h:m:s]: 02:075:13:22:24
Block: 844095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573702 RingCT/type: yes/0
Extra: 01f5812186f6ea5776c446e1c23bc71fb0f15bdc1a6775edd13bcd0dbd884dceea021100000001faf35c9c000000000000000000

1 output(s) for total of 0.979857519000 dcy

stealth address amount amount idx
00: e624ff32cefc829a562d2ab041932dc154b437e0a1756700cd370fea800978e0 0.979857519000 1297381 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": 844105, "vin": [ { "gen": { "height": 844095 } } ], "vout": [ { "amount": 979857519, "target": { "key": "e624ff32cefc829a562d2ab041932dc154b437e0a1756700cd370fea800978e0" } } ], "extra": [ 1, 245, 129, 33, 134, 246, 234, 87, 118, 196, 70, 225, 194, 59, 199, 31, 176, 241, 91, 220, 26, 103, 117, 237, 209, 59, 205, 13, 189, 136, 77, 206, 234, 2, 17, 0, 0, 0, 1, 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