Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018130870a4ebf5de8aee40e5b03b6a5ce13d22e6f16493d18d3882257241173

Tx prefix hash: 1c5988cd4c57c93dd76c9da4b5ed4e9ef72f82471b69b320ecb9f13e9c2ab56e
Tx public key: 53decb35be183e3aa4e3d960ba10dce324bccab7021cb4798c65c3cadafa3430
Timestamp: 1722704192 Timestamp [UCT]: 2024-08-03 16:56:32 Age [y:d:h:m:s]: 00:159:11:03:29
Block: 1079973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114081 RingCT/type: yes/0
Extra: 0153decb35be183e3aa4e3d960ba10dce324bccab7021cb4798c65c3cadafa343002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b0c4dedbefab64c33a97e836895905e0b4f25de8680ce3845a2a6e8384a0a6c 0.600000000000 1553154 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": 1079983, "vin": [ { "gen": { "height": 1079973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b0c4dedbefab64c33a97e836895905e0b4f25de8680ce3845a2a6e8384a0a6c" } } ], "extra": [ 1, 83, 222, 203, 53, 190, 24, 62, 58, 164, 227, 217, 96, 186, 16, 220, 227, 36, 188, 202, 183, 2, 28, 180, 121, 140, 101, 195, 202, 218, 250, 52, 48, 2, 17, 0, 0, 0, 2, 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