Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18738f15e5c8c364f03e5d43641bb4b111a085224179efe23e12f600c7029fa5

Tx prefix hash: 2d3e476a02b2febf4de24f157fcaec7d50a6f9983d41a625e10e8c6dafce4b67
Tx public key: ff9fb7cee93c32aff40ea1f1d8dfdfba6ce7f7dcb223dceee76cef987cc2b310
Timestamp: 1582429402 Timestamp [UCT]: 2020-02-23 03:43:22 Age [y:d:h:m:s]: 04:267:09:13:28
Block: 70495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083759 RingCT/type: yes/0
Extra: 01ff9fb7cee93c32aff40ea1f1d8dfdfba6ce7f7dcb223dceee76cef987cc2b3100211000000018a2ee0d9000000000000000000

1 output(s) for total of 358.444238499000 dcy

stealth address amount amount idx
00: a0755dac663c8faaf1205a373a3a5e144462ee44a34e7898426168e367f80dbf 358.444238499000 130301 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": 70505, "vin": [ { "gen": { "height": 70495 } } ], "vout": [ { "amount": 358444238499, "target": { "key": "a0755dac663c8faaf1205a373a3a5e144462ee44a34e7898426168e367f80dbf" } } ], "extra": [ 1, 255, 159, 183, 206, 233, 60, 50, 175, 244, 14, 161, 241, 216, 223, 223, 186, 108, 231, 247, 220, 178, 35, 220, 238, 231, 108, 239, 152, 124, 194, 179, 16, 2, 17, 0, 0, 0, 1, 138, 46, 224, 217, 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