Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9995f64d409080e25918965b8f60eab2ef6d00b314433b739eddcaa07a85068a

Tx prefix hash: c747e2f8f50a5fd59336fdefc7a8f7caeae80a1f33e569f09ed6dbf5e6eab86d
Tx public key: 0ba0d2f61aca966462d3619fc245ce80b017e61d2d9858554e9b34fdbc31be05
Timestamp: 1736597966 Timestamp [UCT]: 2025-01-11 12:19:26 Age [y:d:h:m:s]: 00:079:07:27:44
Block: 1195011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56469 RingCT/type: yes/0
Extra: 010ba0d2f61aca966462d3619fc245ce80b017e61d2d9858554e9b34fdbc31be050211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d65b604ab9e98f04f27c9e6b5c7f36bfb7b227d729618ea96af3d98d9e9a0505 0.600000000000 1681596 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": 1195021, "vin": [ { "gen": { "height": 1195011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d65b604ab9e98f04f27c9e6b5c7f36bfb7b227d729618ea96af3d98d9e9a0505" } } ], "extra": [ 1, 11, 160, 210, 246, 26, 202, 150, 100, 98, 211, 97, 159, 194, 69, 206, 128, 176, 23, 230, 29, 45, 152, 88, 85, 78, 155, 52, 253, 188, 49, 190, 5, 2, 17, 0, 0, 0, 4, 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