Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53ea1afb43709042246e7420fdd439818080352d5d8428705944f5307b9a8b22

Tx prefix hash: b6a238940ee85a2d5492ea9d4c135788c5f0a0c0cad79fef0d07f5e91b64cb9e
Tx public key: d1e92153f60bae3a6b1af3d4b3c2d654fa8a8059a01d1514991c4203e570e175
Timestamp: 1731172463 Timestamp [UCT]: 2024-11-09 17:14:23 Age [y:d:h:m:s]: 00:168:21:56:31
Block: 1150102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120564 RingCT/type: yes/0
Extra: 01d1e92153f60bae3a6b1af3d4b3c2d654fa8a8059a01d1514991c4203e570e175021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 415f59dd0d9e3c7fec21f727d87d3d33e63d4e84d9a0a28019246b081fbcba4f 0.600000000000 1635309 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": 1150112, "vin": [ { "gen": { "height": 1150102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "415f59dd0d9e3c7fec21f727d87d3d33e63d4e84d9a0a28019246b081fbcba4f" } } ], "extra": [ 1, 209, 233, 33, 83, 246, 11, 174, 58, 107, 26, 243, 212, 179, 194, 214, 84, 250, 138, 128, 89, 160, 29, 21, 20, 153, 28, 66, 3, 229, 112, 225, 117, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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