Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6153843f021aa62233f52488dfbcefa7f9e73a97f5249dd9b6142f292302c695

Tx prefix hash: 6a567c79542e18b6313152614fee09bd4d041a2bd1c8401ed6af6c121b6fe85d
Tx public key: fba3a42cf2fb9b3a102b87cd148c309a60284c4de244073914b51d1e455c7456
Timestamp: 1675154196 Timestamp [UCT]: 2023-01-31 08:36:36 Age [y:d:h:m:s]: 02:068:19:55:34
Block: 686634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 570824 RingCT/type: yes/0
Extra: 01fba3a42cf2fb9b3a102b87cd148c309a60284c4de244073914b51d1e455c74560211000000015029cbac000000000000000000

1 output(s) for total of 3.257590243000 dcy

stealth address amount amount idx
00: f0a09890592cb984e56f99696f0614d2ff108ee49ea8eac2886d9a2a9ab60948 3.257590243000 1129143 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": 686644, "vin": [ { "gen": { "height": 686634 } } ], "vout": [ { "amount": 3257590243, "target": { "key": "f0a09890592cb984e56f99696f0614d2ff108ee49ea8eac2886d9a2a9ab60948" } } ], "extra": [ 1, 251, 163, 164, 44, 242, 251, 155, 58, 16, 43, 135, 205, 20, 140, 48, 154, 96, 40, 76, 77, 226, 68, 7, 57, 20, 181, 29, 30, 69, 92, 116, 86, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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