Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b827048a4b650d712ae710fd87b30595c09721826006ffdaf7a05f81def2251e

Tx prefix hash: 441c4fdf69cc797701035bc1405715dba57a3019ae6cbbc632a2bc151f7295d4
Tx public key: fa409cbc171172da106e7ec272c7a24e91d0fffe74654d23d1f602b334a223f1
Timestamp: 1583004607 Timestamp [UCT]: 2020-02-29 19:30:07 Age [y:d:h:m:s]: 04:251:07:27:01
Block: 74339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073175 RingCT/type: yes/0
Extra: 01fa409cbc171172da106e7ec272c7a24e91d0fffe74654d23d1f602b334a223f102110000025b0aca7173000000000000000000

1 output(s) for total of 348.090637675000 dcy

stealth address amount amount idx
00: c8bca9a9b758cd1aee47f6909ec3a9caa9269191dbdd722f4613e778a967b8a0 348.090637675000 137518 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": 74349, "vin": [ { "gen": { "height": 74339 } } ], "vout": [ { "amount": 348090637675, "target": { "key": "c8bca9a9b758cd1aee47f6909ec3a9caa9269191dbdd722f4613e778a967b8a0" } } ], "extra": [ 1, 250, 64, 156, 188, 23, 17, 114, 218, 16, 110, 126, 194, 114, 199, 162, 78, 145, 208, 255, 254, 116, 101, 77, 35, 209, 246, 2, 179, 52, 162, 35, 241, 2, 17, 0, 0, 2, 91, 10, 202, 113, 115, 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