Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75ed012cac033f9282d51f64d431cfcaf92b0be49ebab928e728f7e7ebb69eb

Tx prefix hash: 4f1ad903d35cbf3dcf4d2bc0c29e78c22f1a1d47c82a41aabc7380b77e198e4a
Tx public key: 2ce320f8b4cf8e293c87238eb2b1f4a781c28b06eb939ec523cd3eb0f96640a0
Timestamp: 1713070606 Timestamp [UCT]: 2024-04-14 04:56:46 Age [y:d:h:m:s]: 01:032:23:40:27
Block: 1000089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284560 RingCT/type: yes/0
Extra: 012ce320f8b4cf8e293c87238eb2b1f4a781c28b06eb939ec523cd3eb0f96640a002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c72dad738ea80645b248f5ae7a4f6d12e275a635b2d7cafbe9717f66fda6516 0.600000000000 1460579 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": 1000099, "vin": [ { "gen": { "height": 1000089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c72dad738ea80645b248f5ae7a4f6d12e275a635b2d7cafbe9717f66fda6516" } } ], "extra": [ 1, 44, 227, 32, 248, 180, 207, 142, 41, 60, 135, 35, 142, 178, 177, 244, 167, 129, 194, 139, 6, 235, 147, 158, 197, 35, 205, 62, 176, 249, 102, 64, 160, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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