Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd9a8c7d637e53d59ce4df46701772643f953a1a183866519085cc3f866a235

Tx prefix hash: 32be0e3b7e25a0c77fdb9e5055b02dd14ef975f35d09072daf5d3438fb391299
Tx public key: db59d98841b3bd36a35ad3d48caeba55e0d991d9d05a6c1178e560dd88bc3afc
Timestamp: 1733473052 Timestamp [UCT]: 2024-12-06 08:17:32 Age [y:d:h:m:s]: 00:100:18:31:09
Block: 1169147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71826 RingCT/type: yes/0
Extra: 01db59d98841b3bd36a35ad3d48caeba55e0d991d9d05a6c1178e560dd88bc3afc021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc2266c8a63ee68f81663cf74d341572494f495e6a1670c2f467998db58b40a1 0.600000000000 1654860 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": 1169157, "vin": [ { "gen": { "height": 1169147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc2266c8a63ee68f81663cf74d341572494f495e6a1670c2f467998db58b40a1" } } ], "extra": [ 1, 219, 89, 217, 136, 65, 179, 189, 54, 163, 90, 211, 212, 140, 174, 186, 85, 224, 217, 145, 217, 208, 90, 108, 17, 120, 229, 96, 221, 136, 188, 58, 252, 2, 17, 0, 0, 0, 4, 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