Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2899d194b7fce7a695a1d54be087fd9172a003460a1e23e96192046cd0b04a

Tx prefix hash: cc7b484cbe72ab21efe3a1166966b9fdbb3452fc91a93e5df9281b2ee179b30b
Tx public key: e763f6b4e899f165048a7556d95920b23b2a5b72dff2ad1f0ceb1da0b22c4f08
Timestamp: 1723016783 Timestamp [UCT]: 2024-08-07 07:46:23 Age [y:d:h:m:s]: 00:077:03:30:02
Block: 1082563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55235 RingCT/type: yes/0
Extra: 01e763f6b4e899f165048a7556d95920b23b2a5b72dff2ad1f0ceb1da0b22c4f0802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e945af161fb8f98d05f782d72088cc3894a2c498ee16e31d7166e6d5e0bb350 0.600000000000 1556392 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": 1082573, "vin": [ { "gen": { "height": 1082563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e945af161fb8f98d05f782d72088cc3894a2c498ee16e31d7166e6d5e0bb350" } } ], "extra": [ 1, 231, 99, 246, 180, 232, 153, 241, 101, 4, 138, 117, 86, 217, 89, 32, 178, 59, 42, 91, 114, 223, 242, 173, 31, 12, 235, 29, 160, 178, 44, 79, 8, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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