Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2eb75d6d47f09965506f9cfac4e44130fbbe55d4f4aa9ee7e57fc92f02c9073

Tx prefix hash: baf3b054619dbab8db205bde452064d3b1602fecf46dc461a64fb4f14b014033
Tx public key: 46d05759fff72032cb376bb4ff38cad7e0ce225cd49425d8c641b2d28de98d48
Timestamp: 1729311249 Timestamp [UCT]: 2024-10-19 04:14:09 Age [y:d:h:m:s]: 00:241:21:03:01
Block: 1134742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172579 RingCT/type: yes/0
Extra: 0146d05759fff72032cb376bb4ff38cad7e0ce225cd49425d8c641b2d28de98d480211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f3acc2a2c400af6f2c56bf6820ce3f49435d5c37eea9e38c7fadf9a6f1d0e3b 0.600000000000 1618069 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": 1134752, "vin": [ { "gen": { "height": 1134742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f3acc2a2c400af6f2c56bf6820ce3f49435d5c37eea9e38c7fadf9a6f1d0e3b" } } ], "extra": [ 1, 70, 208, 87, 89, 255, 247, 32, 50, 203, 55, 107, 180, 255, 56, 202, 215, 224, 206, 34, 92, 212, 148, 37, 216, 198, 65, 178, 210, 141, 233, 141, 72, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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