Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caccd1e35797750f3e5ef93e4be2ac1f3bdd5682f2f6ccfac26a2ac0a7b70a06

Tx prefix hash: 4944058475edcb943d3a452bdd22924dcb4a0999ac4287aff06d60e102a347e6
Tx public key: 068e6f41b7f17a76b89c23ef2bd1aeb055989b4f124172b559f3d5084f7faad8
Timestamp: 1728264061 Timestamp [UCT]: 2024-10-07 01:21:01 Age [y:d:h:m:s]: 00:176:23:31:47
Block: 1126072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126266 RingCT/type: yes/0
Extra: 01068e6f41b7f17a76b89c23ef2bd1aeb055989b4f124172b559f3d5084f7faad802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a71d28f0aec0b999f5ff0b1282f57d0e14ce89c59c44171ad33b458ce4e01956 0.600000000000 1608847 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": 1126082, "vin": [ { "gen": { "height": 1126072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a71d28f0aec0b999f5ff0b1282f57d0e14ce89c59c44171ad33b458ce4e01956" } } ], "extra": [ 1, 6, 142, 111, 65, 183, 241, 122, 118, 184, 156, 35, 239, 43, 209, 174, 176, 85, 152, 155, 79, 18, 65, 114, 181, 89, 243, 213, 8, 79, 127, 170, 216, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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