Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72b092189ad444fde3b173f4679cf6371cf7b745973ed86f0ff55682d27ca95

Tx prefix hash: d809dd987c50a41b1688aae5ece9063cf3ddc513b577518b293692ce41c6a68f
Tx public key: 28260a6ae81aa1090641fd72b39e76fa6f96163161c6ad2c2c1be7df03b7a14a
Timestamp: 1577562396 Timestamp [UCT]: 2019-12-28 19:46:36 Age [y:d:h:m:s]: 05:005:09:59:53
Block: 33773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153890 RingCT/type: yes/0
Extra: 0128260a6ae81aa1090641fd72b39e76fa6f96163161c6ad2c2c1be7df03b7a14a0211000000064943cd9f000000000000000000

1 output(s) for total of 474.363776976000 dcy

stealth address amount amount idx
00: 556d217b72daa586939ae620da225d9e51ca692621a076fc46e949ed9520d429 474.363776976000 56660 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": 33783, "vin": [ { "gen": { "height": 33773 } } ], "vout": [ { "amount": 474363776976, "target": { "key": "556d217b72daa586939ae620da225d9e51ca692621a076fc46e949ed9520d429" } } ], "extra": [ 1, 40, 38, 10, 106, 232, 26, 161, 9, 6, 65, 253, 114, 179, 158, 118, 250, 111, 150, 22, 49, 97, 198, 173, 44, 44, 27, 231, 223, 3, 183, 161, 74, 2, 17, 0, 0, 0, 6, 73, 67, 205, 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