Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc026cceb4ca35c9163084315f49117c51f2622f76c2722f8fef09dacbb03000

Tx prefix hash: 4a78e717cd93d30589e9b754558742e70a4b57676f8eeae66e9583e916d2c61a
Tx public key: 449917aeefad93671c5656af3684d7810995897299e0d4c72167c43df32cf4e9
Timestamp: 1574659042 Timestamp [UCT]: 2019-11-25 05:17:22 Age [y:d:h:m:s]: 05:171:15:28:55
Block: 16932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1265341 RingCT/type: yes/0
Extra: 01449917aeefad93671c5656af3684d7810995897299e0d4c72167c43df32cf4e9021100000001f95225a5000000000000000000

1 output(s) for total of 539.384095495000 dcy

stealth address amount amount idx
00: 08b10f7d069cf5c6f40dfa3824f652c5e4aea4d2f3d95de2cdba66a666bd4a76 539.384095495000 24120 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": 16942, "vin": [ { "gen": { "height": 16932 } } ], "vout": [ { "amount": 539384095495, "target": { "key": "08b10f7d069cf5c6f40dfa3824f652c5e4aea4d2f3d95de2cdba66a666bd4a76" } } ], "extra": [ 1, 68, 153, 23, 174, 239, 173, 147, 103, 28, 86, 86, 175, 54, 132, 215, 129, 9, 149, 137, 114, 153, 224, 212, 199, 33, 103, 196, 61, 243, 44, 244, 233, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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