Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 096760cad5e98b0e6346c10e3d7bd024280cdafe6dc86870253e7bd6f3457254

Tx prefix hash: dcffcd89da78eb81e2d80629c7b28dabb903a8f7b4a04e74f326e1d56be965d4
Tx public key: d7fe0c560d4f9146f4b5a7f93190db0280ba1ccda4f68ca13f2becc0e8a88088
Timestamp: 1712958236 Timestamp [UCT]: 2024-04-12 21:43:56 Age [y:d:h:m:s]: 00:318:09:25:04
Block: 999153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227617 RingCT/type: yes/0
Extra: 01d7fe0c560d4f9146f4b5a7f93190db0280ba1ccda4f68ca13f2becc0e8a880880211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f4bf0d168fb9e5d5206b9f1f02e4cd4293ba4c5d1eee45bdc423f42ae6c1b82 0.600000000000 1459631 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": 999163, "vin": [ { "gen": { "height": 999153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f4bf0d168fb9e5d5206b9f1f02e4cd4293ba4c5d1eee45bdc423f42ae6c1b82" } } ], "extra": [ 1, 215, 254, 12, 86, 13, 79, 145, 70, 244, 181, 167, 249, 49, 144, 219, 2, 128, 186, 28, 205, 164, 246, 140, 161, 63, 43, 236, 192, 232, 168, 128, 136, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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