Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1fc30e53cc13e923be4bb564735b2892c1d644456bc7932515dcb4b0beaeca

Tx prefix hash: 4091853aeb46d739f12ab41fc1d3c094c8617659fa4e2d6423f5dd3aee86a3d7
Tx public key: d0e8e88a54819de7e71fb3b269f274c19a1bbd882075ae2875e79f109ca08d44
Timestamp: 1729664668 Timestamp [UCT]: 2024-10-23 06:24:28 Age [y:d:h:m:s]: 00:032:01:06:46
Block: 1137644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22894 RingCT/type: yes/0
Extra: 01d0e8e88a54819de7e71fb3b269f274c19a1bbd882075ae2875e79f109ca08d44021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9606fabf47f5ba356a9208c363a62413a33c45553780b50ecba534defe024ad 0.600000000000 1621173 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": 1137654, "vin": [ { "gen": { "height": 1137644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9606fabf47f5ba356a9208c363a62413a33c45553780b50ecba534defe024ad" } } ], "extra": [ 1, 208, 232, 232, 138, 84, 129, 157, 231, 231, 31, 179, 178, 105, 242, 116, 193, 154, 27, 189, 136, 32, 117, 174, 40, 117, 231, 159, 16, 156, 160, 141, 68, 2, 17, 0, 0, 0, 6, 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