Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a760e1a90c751afd29e1777697244ebc72528c25670748918d65adbe73a88d3f

Tx prefix hash: bf54003be3050a8f60b78956f1dece81561dd3e7e8095268832838a02e4b7aa2
Tx public key: 4d3c0e023bab0f7e20acd3e050e38d895a71a9bd36179cd64f4b1e765b693568
Timestamp: 1730961182 Timestamp [UCT]: 2024-11-07 06:33:02 Age [y:d:h:m:s]: 00:226:23:57:21
Block: 1148339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161936 RingCT/type: yes/0
Extra: 014d3c0e023bab0f7e20acd3e050e38d895a71a9bd36179cd64f4b1e765b6935680211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac49bcdb4eeeb006635352c0f959de73e3ae0d309eddd86fb2c824820d91e79 0.600000000000 1633158 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": 1148349, "vin": [ { "gen": { "height": 1148339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac49bcdb4eeeb006635352c0f959de73e3ae0d309eddd86fb2c824820d91e79" } } ], "extra": [ 1, 77, 60, 14, 2, 59, 171, 15, 126, 32, 172, 211, 224, 80, 227, 141, 137, 90, 113, 169, 189, 54, 23, 156, 214, 79, 75, 30, 118, 91, 105, 53, 104, 2, 17, 0, 0, 0, 5, 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