Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c63be46614740353e7779ae8228202177e54164af7c1f7984b6efae2945ac7

Tx prefix hash: 08ce1ac2d845f7f95c49651064743dbf130f465823ab6df3e9aa3783e0f930bb
Tx public key: 4d2f56a13af3aad8141bb4fcce309e1566b486b101bf61ec0b82e1a747e77f62
Timestamp: 1714535123 Timestamp [UCT]: 2024-05-01 03:45:23 Age [y:d:h:m:s]: 01:021:20:57:37
Block: 1012249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276587 RingCT/type: yes/0
Extra: 014d2f56a13af3aad8141bb4fcce309e1566b486b101bf61ec0b82e1a747e77f6202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5923c3d77c2cfc0195ae6e4a8e38b75c10627deaf8f2e1e7137125a0a0dc2e3 0.600000000000 1474717 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": 1012259, "vin": [ { "gen": { "height": 1012249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5923c3d77c2cfc0195ae6e4a8e38b75c10627deaf8f2e1e7137125a0a0dc2e3" } } ], "extra": [ 1, 77, 47, 86, 161, 58, 243, 170, 216, 20, 27, 180, 252, 206, 48, 158, 21, 102, 180, 134, 177, 1, 191, 97, 236, 11, 130, 225, 167, 71, 231, 127, 98, 2, 17, 0, 0, 0, 2, 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