Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b71a9939337ed5b98cb2c52867279ff77bc292b482f2e4bc408f9517d131217

Tx prefix hash: 607441f8f4e473b56d3edd2ffd86cf5a48c5bac4d9e2af291faff5c8b7f37124
Tx public key: cc9808937b8b5965cda1699377d608611d4d441025a61f59f5ff10f4c276a7ad
Timestamp: 1740511869 Timestamp [UCT]: 2025-02-25 19:31:09 Age [y:d:h:m:s]: 00:014:22:25:09
Block: 1227144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10708 RingCT/type: yes/0
Extra: 01cc9808937b8b5965cda1699377d608611d4d441025a61f59f5ff10f4c276a7ad021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd36b6608a5b97d040fbb3d122f938832df917b1a2c6d0c35f420ec6dfb64d7 0.600000000000 1714017 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": 1227154, "vin": [ { "gen": { "height": 1227144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd36b6608a5b97d040fbb3d122f938832df917b1a2c6d0c35f420ec6dfb64d7" } } ], "extra": [ 1, 204, 152, 8, 147, 123, 139, 89, 101, 205, 161, 105, 147, 119, 214, 8, 97, 29, 77, 68, 16, 37, 166, 31, 89, 245, 255, 16, 244, 194, 118, 167, 173, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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