Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd110f48ccfedbd8a234d88604809c38ead3e5178769317ea589f13b6981a354

Tx prefix hash: c38d5c05821de953939253bde4abc3e50fe85e281ab95c35e39f0035a424d51f
Tx public key: c61282544ad7f04928b113121e51ae6eeb344c33407902c316b15f3b05d93b91
Timestamp: 1728734604 Timestamp [UCT]: 2024-10-12 12:03:24 Age [y:d:h:m:s]: 01:028:06:50:48
Block: 1129971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278584 RingCT/type: yes/0
Extra: 01c61282544ad7f04928b113121e51ae6eeb344c33407902c316b15f3b05d93b9102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 752ed71091b0f12f98fee0f6a44d75f56ee845afe7ea2155068f6ec44424a616 0.600000000000 1612842 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": 1129981, "vin": [ { "gen": { "height": 1129971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "752ed71091b0f12f98fee0f6a44d75f56ee845afe7ea2155068f6ec44424a616" } } ], "extra": [ 1, 198, 18, 130, 84, 74, 215, 240, 73, 40, 177, 19, 18, 30, 81, 174, 110, 235, 52, 76, 51, 64, 121, 2, 195, 22, 177, 95, 59, 5, 217, 59, 145, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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