Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9db4dd6e3c4545b240ffd3fc2f41a773e3e8d96c33e8af3331396cee9e61b6a

Tx prefix hash: 4ce3d37a1e89a26d3bffe900cede156db3e9d13329f3ab450329f1db784e90f3
Tx public key: 2cb6fcfa5c60d91d76f159342ac40b4992729647afc8296d6cb6e8ecab966089
Timestamp: 1692481761 Timestamp [UCT]: 2023-08-19 21:49:21 Age [y:d:h:m:s]: 01:176:22:48:18
Block: 829574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387608 RingCT/type: yes/0
Extra: 012cb6fcfa5c60d91d76f159342ac40b4992729647afc8296d6cb6e8ecab966089021100000004faf35c9c000000000000000000

1 output(s) for total of 1.094654463000 dcy

stealth address amount amount idx
00: 687878237f93c0e89b9df3f05bf1421cd11abc5a163136e87412022d003ac09a 1.094654463000 1281944 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": 829584, "vin": [ { "gen": { "height": 829574 } } ], "vout": [ { "amount": 1094654463, "target": { "key": "687878237f93c0e89b9df3f05bf1421cd11abc5a163136e87412022d003ac09a" } } ], "extra": [ 1, 44, 182, 252, 250, 92, 96, 217, 29, 118, 241, 89, 52, 42, 196, 11, 73, 146, 114, 150, 71, 175, 200, 41, 109, 108, 182, 232, 236, 171, 150, 96, 137, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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