Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40319795f71d0396518fd57d7731568571ee0968eb1dce827f0938caea4b4540

Tx prefix hash: 28b6f7c9915dab920ef40d245badb4d2ee22c76d80e86685a592c72e3c77f4b8
Tx public key: 1070b63e7fe5132f5ce5e8066c546f6309dac8eb29dc99f5d3dba591b0d568f4
Timestamp: 1714477038 Timestamp [UCT]: 2024-04-30 11:37:18 Age [y:d:h:m:s]: 00:303:08:01:40
Block: 1011766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216811 RingCT/type: yes/0
Extra: 011070b63e7fe5132f5ce5e8066c546f6309dac8eb29dc99f5d3dba591b0d568f402110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819583f5b73c859664b129cb019fe3a68f32aec4f371eb05a91b05b6b81368b2 0.600000000000 1474084 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": 1011776, "vin": [ { "gen": { "height": 1011766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819583f5b73c859664b129cb019fe3a68f32aec4f371eb05a91b05b6b81368b2" } } ], "extra": [ 1, 16, 112, 182, 62, 127, 229, 19, 47, 92, 229, 232, 6, 108, 84, 111, 99, 9, 218, 200, 235, 41, 220, 153, 245, 211, 219, 165, 145, 176, 213, 104, 244, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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