Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c55387922f5ddf77481b71973a4e0b529bb0051690244843d45fe3f21609451

Tx prefix hash: 0d83a64ac1dc30244b2f2afeb8352c38ceb591d3eb9de082c6a47ff49c502227
Tx public key: 1f81d2bfd768bdaa9466fa082b6fd6238672e43b3cf7aacea897c379c9a5f362
Timestamp: 1727825905 Timestamp [UCT]: 2024-10-01 23:38:25 Age [y:d:h:m:s]: 00:112:23:41:27
Block: 1122443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80728 RingCT/type: yes/0
Extra: 011f81d2bfd768bdaa9466fa082b6fd6238672e43b3cf7aacea897c379c9a5f36202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da274ce4bef70c5af11551b32345c85044df72e81982680750abcabefb8e282b 0.600000000000 1604880 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": 1122453, "vin": [ { "gen": { "height": 1122443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da274ce4bef70c5af11551b32345c85044df72e81982680750abcabefb8e282b" } } ], "extra": [ 1, 31, 129, 210, 191, 215, 104, 189, 170, 148, 102, 250, 8, 43, 111, 214, 35, 134, 114, 228, 59, 60, 247, 170, 206, 168, 151, 195, 121, 201, 165, 243, 98, 2, 17, 0, 0, 0, 7, 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