Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16c7bd154debed8fbeea70060e7df28e99e803f064ed6fbec76a9066bdb97f3

Tx prefix hash: fc4cbed1d096524e7bf3ffa812f4e1db91c761979de8c5b2a5908d66f7112cc9
Tx public key: b69fa4b0ce8f59c97722b4c9cfbbf21d43c9e8df2751fe08dfb29277defc1fd8
Timestamp: 1719185518 Timestamp [UCT]: 2024-06-23 23:31:58 Age [y:d:h:m:s]: 00:320:11:39:06
Block: 1050798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229033 RingCT/type: yes/0
Extra: 01b69fa4b0ce8f59c97722b4c9cfbbf21d43c9e8df2751fe08dfb29277defc1fd80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a02b8727e0c2a1a5f1630fa73f182a9c6858621c27833fc878b4a2843391531 0.600000000000 1520973 of 15

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": 1050808, "vin": [ { "gen": { "height": 1050798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a02b8727e0c2a1a5f1630fa73f182a9c6858621c27833fc878b4a2843391531" } } ], "extra": [ 1, 182, 159, 164, 176, 206, 143, 89, 201, 119, 34, 180, 201, 207, 187, 242, 29, 67, 201, 232, 223, 39, 81, 254, 8, 223, 178, 146, 119, 222, 252, 31, 216, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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