Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae319bc4a72445f45522607fe9376da931e93a6b8ba24736bd50f6683ed8f9c5

Tx prefix hash: a6af244aee204e72ae23a4e725dda2efb9789497329576faae86ccba553f7ffc
Tx public key: db3197032feaf6954d7a4a9077f1f489419f154acc1eb8cc1fc815a2e517c460
Timestamp: 1710866241 Timestamp [UCT]: 2024-03-19 16:37:21 Age [y:d:h:m:s]: 01:015:22:18:51
Block: 981856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272345 RingCT/type: yes/0
Extra: 01db3197032feaf6954d7a4a9077f1f489419f154acc1eb8cc1fc815a2e517c46002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2ec57c9ebd1d3a1de71857243c32c83aba9f515c52d16f879994c3d7d219f4 0.600000000000 1441955 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": 981866, "vin": [ { "gen": { "height": 981856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2ec57c9ebd1d3a1de71857243c32c83aba9f515c52d16f879994c3d7d219f4" } } ], "extra": [ 1, 219, 49, 151, 3, 47, 234, 246, 149, 77, 122, 74, 144, 119, 241, 244, 137, 65, 159, 21, 74, 204, 30, 184, 204, 31, 200, 21, 162, 229, 23, 196, 96, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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