Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fa53cdb5cde4ef773aa11508cb62d5073ba78fc8ff6635244c6011327c7d087

Tx prefix hash: 0530d5fb8112ce6961414bdc81975d0d330ab54741324454bd27975207bee457
Tx public key: 5277a5f1fb53177e27fc0aa461a1b78f930b3122930b572fa80a63c182f7d328
Timestamp: 1719129396 Timestamp [UCT]: 2024-06-23 07:56:36 Age [y:d:h:m:s]: 00:307:00:17:48
Block: 1050321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219413 RingCT/type: yes/0
Extra: 015277a5f1fb53177e27fc0aa461a1b78f930b3122930b572fa80a63c182f7d3280211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6d011b4a3d2d71bb8d5c8c334567da00ab3d843e1a5f6695b13967280952051 0.600000000000 1520486 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": 1050331, "vin": [ { "gen": { "height": 1050321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6d011b4a3d2d71bb8d5c8c334567da00ab3d843e1a5f6695b13967280952051" } } ], "extra": [ 1, 82, 119, 165, 241, 251, 83, 23, 126, 39, 252, 10, 164, 97, 161, 183, 143, 147, 11, 49, 34, 147, 11, 87, 47, 168, 10, 99, 193, 130, 247, 211, 40, 2, 17, 0, 0, 0, 1, 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