Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a95a13a25dc47e031648086aecd29986fa21014e600e7ecd18e213414c7966

Tx prefix hash: e48792fca525df25908e64226c5c9536507befcb41825260e5cc2879a8c4783c
Tx public key: 1035ad17b1bfc15a3e3c7e9e81a5335987aedadc530b4c7e4c2d6ff67987c8ef
Timestamp: 1714564063 Timestamp [UCT]: 2024-05-01 11:47:43 Age [y:d:h:m:s]: 01:190:23:40:07
Block: 1012491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395119 RingCT/type: yes/0
Extra: 011035ad17b1bfc15a3e3c7e9e81a5335987aedadc530b4c7e4c2d6ff67987c8ef0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1d06afb8ff4c081bb0a91f68edb1578c06471ca62692014e7fa172e142952ad 0.600000000000 1475037 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": 1012501, "vin": [ { "gen": { "height": 1012491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1d06afb8ff4c081bb0a91f68edb1578c06471ca62692014e7fa172e142952ad" } } ], "extra": [ 1, 16, 53, 173, 23, 177, 191, 193, 90, 62, 60, 126, 158, 129, 165, 51, 89, 135, 174, 218, 220, 83, 11, 76, 126, 76, 45, 111, 246, 121, 135, 200, 239, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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