Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aff7273da41391a80ad73ac3ffa5c6aa7092f94180307f6881616b59315b32c

Tx prefix hash: 1bd151736e9249feb44367123907d2ead47b4b898e903c008788f332b8e78861
Tx public key: 31f86c6b0a0229a1ed5603e37dc5bc88fe0888173de954fe9a4ebbe7624f82ac
Timestamp: 1577557416 Timestamp [UCT]: 2019-12-28 18:23:36 Age [y:d:h:m:s]: 05:002:07:57:33
Block: 33702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151722 RingCT/type: yes/0
Extra: 0131f86c6b0a0229a1ed5603e37dc5bc88fe0888173de954fe9a4ebbe7624f82ac021100000142c3a1a09f000000000000000000

1 output(s) for total of 474.604815602000 dcy

stealth address amount amount idx
00: b60d8a9c8cdf2884d3f958a717b0cead2aa2c64e0c064d54724b09e79603772d 474.604815602000 56523 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": 33712, "vin": [ { "gen": { "height": 33702 } } ], "vout": [ { "amount": 474604815602, "target": { "key": "b60d8a9c8cdf2884d3f958a717b0cead2aa2c64e0c064d54724b09e79603772d" } } ], "extra": [ 1, 49, 248, 108, 107, 10, 2, 41, 161, 237, 86, 3, 227, 125, 197, 188, 136, 254, 8, 136, 23, 61, 233, 84, 254, 154, 78, 187, 231, 98, 79, 130, 172, 2, 17, 0, 0, 1, 66, 195, 161, 160, 159, 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