Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b645a2955c9cfe81aad3fa4d28fa4b0c87389336c73824d53e2db9dc221443

Tx prefix hash: 75bccfd9115678a470bf4a633760742809c99d5570cc4284fa6ea67da54b16fa
Tx public key: 32d8c6f534a93b9370035dfe825db4863d299b7bf82a268298a3d9f48e6527a3
Timestamp: 1736353699 Timestamp [UCT]: 2025-01-08 16:28:19 Age [y:d:h:m:s]: 00:071:13:51:30
Block: 1192995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50945 RingCT/type: yes/0
Extra: 0132d8c6f534a93b9370035dfe825db4863d299b7bf82a268298a3d9f48e6527a3021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 567ce635bb487c2cf4f04d42c610e494aa63653e9e00b84cf9d8430af9caf87d 0.600000000000 1679552 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": 1193005, "vin": [ { "gen": { "height": 1192995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "567ce635bb487c2cf4f04d42c610e494aa63653e9e00b84cf9d8430af9caf87d" } } ], "extra": [ 1, 50, 216, 198, 245, 52, 169, 59, 147, 112, 3, 93, 254, 130, 93, 180, 134, 61, 41, 155, 123, 248, 42, 38, 130, 152, 163, 217, 244, 142, 101, 39, 163, 2, 17, 0, 0, 0, 8, 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