Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15dffd90614c246d8aa54cf24c23a3fbc979fc4d15bc0e245e3095572dafd926

Tx prefix hash: 2af907d01c1a65b62cff6fb2832af9741cc5fa0027ca47431c2b58ee5c5e6695
Tx public key: d255485fd7e133f8266dc25c77c6aa490f77220a67f84a209a22fe7da4886597
Timestamp: 1580975221 Timestamp [UCT]: 2020-02-06 07:47:01 Age [y:d:h:m:s]: 05:272:18:24:34
Block: 59556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1344918 RingCT/type: yes/0
Extra: 01d255485fd7e133f8266dc25c77c6aa490f77220a67f84a209a22fe7da488659702110000000503d36d11000000000000000000

1 output(s) for total of 389.660600138000 dcy

stealth address amount amount idx
00: 33d664a643d67881d76a34ebcb5c6d1ce42bf164b487c24fa87305abf85b70e0 389.660600138000 109978 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": 59566, "vin": [ { "gen": { "height": 59556 } } ], "vout": [ { "amount": 389660600138, "target": { "key": "33d664a643d67881d76a34ebcb5c6d1ce42bf164b487c24fa87305abf85b70e0" } } ], "extra": [ 1, 210, 85, 72, 95, 215, 225, 51, 248, 38, 109, 194, 92, 119, 198, 170, 73, 15, 119, 34, 10, 103, 248, 74, 32, 154, 34, 254, 125, 164, 136, 101, 151, 2, 17, 0, 0, 0, 5, 3, 211, 109, 17, 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