Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 584dd007a95fcac7bc1c6d3d4c984eaf35128a4429caaeb6abbfdc5209b1e9f5

Tx prefix hash: 877a4cef1d866f94c8ebb391dfa6e2e2fc3000e1f0cfab1660ba9436714b1a7c
Tx public key: 5b5d0fa861628c2755863b37e20173a00901c98c0df0f4c591c96d29a398090b
Timestamp: 1706059031 Timestamp [UCT]: 2024-01-24 01:17:11 Age [y:d:h:m:s]: 01:145:04:52:40
Block: 941946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364814 RingCT/type: yes/0
Extra: 015b5d0fa861628c2755863b37e20173a00901c98c0df0f4c591c96d29a398090b02110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3cedf34215b387c8c6503485d837e8e7afbdf897d0891062892cd0e30e498de 0.600000000000 1400106 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": 941956, "vin": [ { "gen": { "height": 941946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3cedf34215b387c8c6503485d837e8e7afbdf897d0891062892cd0e30e498de" } } ], "extra": [ 1, 91, 93, 15, 168, 97, 98, 140, 39, 85, 134, 59, 55, 226, 1, 115, 160, 9, 1, 201, 140, 13, 240, 244, 197, 145, 201, 109, 41, 163, 152, 9, 11, 2, 17, 0, 0, 0, 14, 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