Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f12ab8ebf2b16829aea73f77bc54f6aeb198883880b8d25a7b0d308cd51d1180

Tx prefix hash: 5c6a0c2b65aa83efee0d59acc17c1c1ae34804134c8755d8bb5a7b4c37199b54
Tx public key: 1ae9a10d5bef2164b1479e9be23a45fa2debbdd2420647656eae6f1f0b0b3994
Timestamp: 1733291516 Timestamp [UCT]: 2024-12-04 05:51:56 Age [y:d:h:m:s]: 00:108:06:10:44
Block: 1167645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77171 RingCT/type: yes/0
Extra: 011ae9a10d5bef2164b1479e9be23a45fa2debbdd2420647656eae6f1f0b0b39940211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cdf96a6eae3028dd7448caf478ffcc935798af6c4f75b83beb4507777e8d4b7 0.600000000000 1653344 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": 1167655, "vin": [ { "gen": { "height": 1167645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cdf96a6eae3028dd7448caf478ffcc935798af6c4f75b83beb4507777e8d4b7" } } ], "extra": [ 1, 26, 233, 161, 13, 91, 239, 33, 100, 177, 71, 158, 155, 226, 58, 69, 250, 45, 235, 189, 210, 66, 6, 71, 101, 110, 174, 111, 31, 11, 11, 57, 148, 2, 17, 0, 0, 0, 4, 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