Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f164ede31f0fbd1ac6b51e9372fba992afd499cd862e22599f32b1266c3f8a17

Tx prefix hash: 8568d2c69378b96d9bc0302c81de1d001ee3d72319f587e1ca41b283c6d76af7
Tx public key: 3aa967c4b74111f8097b5f8733e608f4085169bf8152fdffcdcf8ae58373e2fd
Timestamp: 1716140314 Timestamp [UCT]: 2024-05-19 17:38:34 Age [y:d:h:m:s]: 00:332:01:07:36
Block: 1025552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237342 RingCT/type: yes/0
Extra: 013aa967c4b74111f8097b5f8733e608f4085169bf8152fdffcdcf8ae58373e2fd02110000000552d47e94000000000000000000

1 output(s) for total of 0.615570000000 dcy

stealth address amount amount idx
00: b5e35151d1406c0c751864abaf01a8a99ad2fd57716592f2bcdc179d6884ee20 0.615570000000 1492141 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": 1025562, "vin": [ { "gen": { "height": 1025552 } } ], "vout": [ { "amount": 615570000, "target": { "key": "b5e35151d1406c0c751864abaf01a8a99ad2fd57716592f2bcdc179d6884ee20" } } ], "extra": [ 1, 58, 169, 103, 196, 183, 65, 17, 248, 9, 123, 95, 135, 51, 230, 8, 244, 8, 81, 105, 191, 129, 82, 253, 255, 205, 207, 138, 229, 131, 115, 226, 253, 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