Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fb697840dce6faac3d6739bfb379113d841c623912a0d864b8d812be56e1b83

Tx prefix hash: 973760662d965c23c31c2f8438a1011cb253bac10a374fd5f37bf097c5836601
Tx public key: b4d740fe4b5c89a402516c9d35da54418c6bc6ad45bacddfda5cb1608d8d4e0b
Timestamp: 1727520179 Timestamp [UCT]: 2024-09-28 10:42:59 Age [y:d:h:m:s]: 00:061:09:51:02
Block: 1119904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43891 RingCT/type: yes/0
Extra: 01b4d740fe4b5c89a402516c9d35da54418c6bc6ad45bacddfda5cb1608d8d4e0b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248db5d889404c42ff290c9399e3e0f929495127ac48f075b6086b3150bbfe4d 0.600000000000 1601631 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": 1119914, "vin": [ { "gen": { "height": 1119904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248db5d889404c42ff290c9399e3e0f929495127ac48f075b6086b3150bbfe4d" } } ], "extra": [ 1, 180, 215, 64, 254, 75, 92, 137, 164, 2, 81, 108, 157, 53, 218, 84, 65, 140, 107, 198, 173, 69, 186, 205, 223, 218, 92, 177, 96, 141, 141, 78, 11, 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