Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6589f43d1c108889d1b6d909952418be8902f6119efbc4450fadd3c9889f627

Tx prefix hash: 9dfe928cd8572f246181d0078bab2cfe11777efc2bc1d479ac21844233aeae3e
Tx public key: 3a35c328bbb8da5c47c0999829e0c7fe924dea919075ab5a358934e4050d0d1a
Timestamp: 1722258545 Timestamp [UCT]: 2024-07-29 13:09:05 Age [y:d:h:m:s]: 00:149:06:57:40
Block: 1076285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106812 RingCT/type: yes/0
Extra: 013a35c328bbb8da5c47c0999829e0c7fe924dea919075ab5a358934e4050d0d1a021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69b5c2c71537b90706df8323c228444d45edcfd3f3a8649d43b1f8475ee04f42 0.600000000000 1548822 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": 1076295, "vin": [ { "gen": { "height": 1076285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69b5c2c71537b90706df8323c228444d45edcfd3f3a8649d43b1f8475ee04f42" } } ], "extra": [ 1, 58, 53, 195, 40, 187, 184, 218, 92, 71, 192, 153, 152, 41, 224, 199, 254, 146, 77, 234, 145, 144, 117, 171, 90, 53, 137, 52, 228, 5, 13, 13, 26, 2, 17, 0, 0, 0, 19, 233, 20, 221, 21, 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