Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632a236fe9aff534a56e323ab9b9e68e12f06e06b967dc734317d58e8dc267bc

Tx prefix hash: 21259e99aeb7e767f2977c5f22767dcdc0e0d4dd547c71f918e16ae064a28be1
Tx public key: 92b940e86f787b08938bd4c80f372cc411b16a95ed9087ac4833e10bfbff099a
Timestamp: 1729891022 Timestamp [UCT]: 2024-10-25 21:17:02 Age [y:d:h:m:s]: 00:157:13:50:06
Block: 1139526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112400 RingCT/type: yes/0
Extra: 0192b940e86f787b08938bd4c80f372cc411b16a95ed9087ac4833e10bfbff099a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8437cd8544e262aea5781d778d8b9cb3bc7e8ce62b81d574849e477ae5323f5 0.600000000000 1623313 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": 1139536, "vin": [ { "gen": { "height": 1139526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8437cd8544e262aea5781d778d8b9cb3bc7e8ce62b81d574849e477ae5323f5" } } ], "extra": [ 1, 146, 185, 64, 232, 111, 120, 123, 8, 147, 139, 212, 200, 15, 55, 44, 196, 17, 177, 106, 149, 237, 144, 135, 172, 72, 51, 225, 11, 251, 255, 9, 154, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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