Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4401b0708186961936b9a14123671412307d98c1f9fe416aed40ddc7dc8dc8ce

Tx prefix hash: 44c123c24654a94da9b6a00a8c11fce423d7283e5ff45ee2d0236d55e25e4476
Tx public key: b64ed5c502731b67e1ee0b8baaa2fc1b90188770a7a809193dfe1c4aa8f226f6
Timestamp: 1583636783 Timestamp [UCT]: 2020-03-08 03:06:23 Age [y:d:h:m:s]: 04:330:22:41:55
Block: 78409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131051 RingCT/type: yes/0
Extra: 01b64ed5c502731b67e1ee0b8baaa2fc1b90188770a7a809193dfe1c4aa8f226f6021100000008a3671f4b000000000000000000

1 output(s) for total of 337.442069705000 dcy

stealth address amount amount idx
00: 9353476a3f722e5a3c118e5aeafd3cad05204a56f50dc4b90504c32b10baa010 337.442069705000 143859 of 0

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": 78419, "vin": [ { "gen": { "height": 78409 } } ], "vout": [ { "amount": 337442069705, "target": { "key": "9353476a3f722e5a3c118e5aeafd3cad05204a56f50dc4b90504c32b10baa010" } } ], "extra": [ 1, 182, 78, 213, 197, 2, 115, 27, 103, 225, 238, 11, 139, 170, 162, 252, 27, 144, 24, 135, 112, 167, 168, 9, 25, 61, 254, 28, 74, 168, 242, 38, 246, 2, 17, 0, 0, 0, 8, 163, 103, 31, 75, 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