Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8183288df53d4affd4e773c860ef3138414cf6aceb2a2cfab9b0dd1c6389788c

Tx prefix hash: c1f9ae88258a9db3f070768db9f5cbb3955f5ba88a872e963cd25119f2e91527
Tx public key: f3e331e76f0fd1872705e256bc20e53e4a219355fac0e83b021ace2626e4c86f
Timestamp: 1720100970 Timestamp [UCT]: 2024-07-04 13:49:30 Age [y:d:h:m:s]: 00:276:03:59:12
Block: 1058385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197317 RingCT/type: yes/0
Extra: 01f3e331e76f0fd1872705e256bc20e53e4a219355fac0e83b021ace2626e4c86f0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57cfccd67a681ca7e4b27142be4494e119c7cad8a59021c637f677c2d143f55 0.600000000000 1528840 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": 1058395, "vin": [ { "gen": { "height": 1058385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57cfccd67a681ca7e4b27142be4494e119c7cad8a59021c637f677c2d143f55" } } ], "extra": [ 1, 243, 227, 49, 231, 111, 15, 209, 135, 39, 5, 226, 86, 188, 32, 229, 62, 74, 33, 147, 85, 250, 192, 232, 59, 2, 26, 206, 38, 38, 228, 200, 111, 2, 17, 0, 0, 0, 6, 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