Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c9a390047ec3c897811a3d45f6d9d0a593baddc7ff577f0beadb1553469e821

Tx prefix hash: f8526a52d302d92ee40bd0b5f0c4e4221b1ff86af4391f1cffb44e293c0f839d
Tx public key: d37cf86b459081d6a54e7184e5735990f46c2a460ed5de672b51b6a3fde6e01c
Timestamp: 1724467226 Timestamp [UCT]: 2024-08-24 02:40:26 Age [y:d:h:m:s]: 00:225:18:55:23
Block: 1094599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161210 RingCT/type: yes/0
Extra: 01d37cf86b459081d6a54e7184e5735990f46c2a460ed5de672b51b6a3fde6e01c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c28344fee0338a6dbb31c699750c4a3f0842310a47f613ef9c4d0c2a57c8f4b2 0.600000000000 1569716 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": 1094609, "vin": [ { "gen": { "height": 1094599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c28344fee0338a6dbb31c699750c4a3f0842310a47f613ef9c4d0c2a57c8f4b2" } } ], "extra": [ 1, 211, 124, 248, 107, 69, 144, 129, 214, 165, 78, 113, 132, 229, 115, 89, 144, 244, 108, 42, 70, 14, 213, 222, 103, 43, 81, 182, 163, 253, 230, 224, 28, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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