Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 601fe5658fa534680227b5955b24763382996947236e0586c95f0ef6a536d142

Tx prefix hash: ddc436dc6e716e4aefd5297f0d80617146f202a6803593f834c1ef6e6d61ef30
Tx public key: 8492814405c306a619de3ed3e22a14a169ad292ad7f2c04dc623956ca6c97416
Timestamp: 1665181275 Timestamp [UCT]: 2022-10-07 22:21:15 Age [y:d:h:m:s]: 02:033:22:54:08
Block: 604208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546010 RingCT/type: yes/0
Extra: 018492814405c306a619de3ed3e22a14a169ad292ad7f2c04dc623956ca6c9741602110000000375e3f0e9000000000000000000

1 output(s) for total of 6.109534632000 dcy

stealth address amount amount idx
00: dd10cb10e09b11e734d7fd30b0de51fccfe19bbfd2f54f59b6946c55f7d29bb7 6.109534632000 1040529 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": 604218, "vin": [ { "gen": { "height": 604208 } } ], "vout": [ { "amount": 6109534632, "target": { "key": "dd10cb10e09b11e734d7fd30b0de51fccfe19bbfd2f54f59b6946c55f7d29bb7" } } ], "extra": [ 1, 132, 146, 129, 68, 5, 195, 6, 166, 25, 222, 62, 211, 226, 42, 20, 161, 105, 173, 41, 42, 215, 242, 192, 77, 198, 35, 149, 108, 166, 201, 116, 22, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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