Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1e86bf94410e574ea4a0b8af80d1a6d0dcc79711c76950ee1b8b747641c6e79

Tx prefix hash: f2241ebb2a8f6e0b36ea63e0b374a7cd76c591caf4a5405a21d913dda6baf088
Tx public key: b366c5a2174e9932f48a4657b204ad87354a531684ecde42378e2141488d1df9
Timestamp: 1712664461 Timestamp [UCT]: 2024-04-09 12:07:41 Age [y:d:h:m:s]: 00:347:10:40:36
Block: 996715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248434 RingCT/type: yes/0
Extra: 01b366c5a2174e9932f48a4657b204ad87354a531684ecde42378e2141488d1df9021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7bbb2f9a9c01b4065929ed7e4fc556f3fa97fa3919f16767d05d73ac13ee8e 0.600000000000 1457141 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": 996725, "vin": [ { "gen": { "height": 996715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7bbb2f9a9c01b4065929ed7e4fc556f3fa97fa3919f16767d05d73ac13ee8e" } } ], "extra": [ 1, 179, 102, 197, 162, 23, 78, 153, 50, 244, 138, 70, 87, 178, 4, 173, 135, 53, 74, 83, 22, 132, 236, 222, 66, 55, 142, 33, 65, 72, 141, 29, 249, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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