Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba331215c8a3f0a95d61db48535b040b71b8e0f6a883466a5279c444c6cbae88

Tx prefix hash: 1bc9943a7ce1bb50ffe414a21c30114e3fc4bc35cc79a62d5d7ef1d13ffa4910
Tx public key: 687c54d5e3b4e2be5d35175a8babc2fe0b638561af100e44629d60c844535dca
Timestamp: 1736613315 Timestamp [UCT]: 2025-01-11 16:35:15 Age [y:d:h:m:s]: 00:067:05:35:22
Block: 1195141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47854 RingCT/type: yes/0
Extra: 01687c54d5e3b4e2be5d35175a8babc2fe0b638561af100e44629d60c844535dca02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f68c06c01d9c5bffd25fcf29dfff590b2119a8614acefccce5ad7ed6f56e3a4a 0.600000000000 1681730 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": 1195151, "vin": [ { "gen": { "height": 1195141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f68c06c01d9c5bffd25fcf29dfff590b2119a8614acefccce5ad7ed6f56e3a4a" } } ], "extra": [ 1, 104, 124, 84, 213, 227, 180, 226, 190, 93, 53, 23, 90, 139, 171, 194, 254, 11, 99, 133, 97, 175, 16, 14, 68, 98, 157, 96, 200, 68, 83, 93, 202, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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