Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9e68afdf7d377ea7f8ad16b8259c9be50f03d92c847c14f8dc73b150bafd410

Tx prefix hash: a3aba4e474edf28185aa40d33a0b99843ea92c15c670f69bba05d809e6f9a0ae
Tx public key: fde9e020be751dbedca09b933325670863532602a43cad8c32a2bb985ac657d9
Timestamp: 1711753721 Timestamp [UCT]: 2024-03-29 23:08:41 Age [y:d:h:m:s]: 01:012:14:29:01
Block: 989206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269967 RingCT/type: yes/0
Extra: 01fde9e020be751dbedca09b933325670863532602a43cad8c32a2bb985ac657d90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601e4f1e45c93e15be9f25d28f0966e32558c02efe8cc6f54e3a277b271c2140 0.600000000000 1449501 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": 989216, "vin": [ { "gen": { "height": 989206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601e4f1e45c93e15be9f25d28f0966e32558c02efe8cc6f54e3a277b271c2140" } } ], "extra": [ 1, 253, 233, 224, 32, 190, 117, 29, 190, 220, 160, 155, 147, 51, 37, 103, 8, 99, 83, 38, 2, 164, 60, 173, 140, 50, 162, 187, 152, 90, 198, 87, 217, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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