Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03940287da5fe8274e96e301b4355c6f7dc884de2bff9c83e973a8f358c6cdd5

Tx prefix hash: f4d173c44a4a1c0da5758e55c43ff26f58eeb490a345d318ce65da80b5ad7611
Tx public key: 152d906a71238b1029a1baac6b3988f4e571e524c47a33ff3611fd2c609eacbb
Timestamp: 1731415939 Timestamp [UCT]: 2024-11-12 12:52:19 Age [y:d:h:m:s]: 00:132:01:25:05
Block: 1152105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94206 RingCT/type: yes/0
Extra: 01152d906a71238b1029a1baac6b3988f4e571e524c47a33ff3611fd2c609eacbb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60a0b4b74ef99e1c8a054b7ef0859567d7b44d0b780bf21e552bd0f57fadb7a8 0.600000000000 1637696 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": 1152115, "vin": [ { "gen": { "height": 1152105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60a0b4b74ef99e1c8a054b7ef0859567d7b44d0b780bf21e552bd0f57fadb7a8" } } ], "extra": [ 1, 21, 45, 144, 106, 113, 35, 139, 16, 41, 161, 186, 172, 107, 57, 136, 244, 229, 113, 229, 36, 196, 122, 51, 255, 54, 17, 253, 44, 96, 158, 172, 187, 2, 17, 0, 0, 0, 2, 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