Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f4ebd836e7840fdfcef7c58340c4aea6c689e16be464c37ee5700d23bd8b8c

Tx prefix hash: 95ce6903788b9a389b1e1b8b389b058ad714355d4c41a521d909237a1bb9e758
Tx public key: 8d3de7f7707ac4880f3c4d678e64629972f746733e49bcad221b1593f3c4cb9b
Timestamp: 1714828706 Timestamp [UCT]: 2024-05-04 13:18:26 Age [y:d:h:m:s]: 00:343:07:25:20
Block: 1014694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245396 RingCT/type: yes/0
Extra: 018d3de7f7707ac4880f3c4d678e64629972f746733e49bcad221b1593f3c4cb9b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b41f4fb1b6f0df85cd635c73f229233e0c9ad47b8766e3dfbf45d7f0b209df75 0.600000000000 1477851 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": 1014704, "vin": [ { "gen": { "height": 1014694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b41f4fb1b6f0df85cd635c73f229233e0c9ad47b8766e3dfbf45d7f0b209df75" } } ], "extra": [ 1, 141, 61, 231, 247, 112, 122, 196, 136, 15, 60, 77, 103, 142, 100, 98, 153, 114, 247, 70, 115, 62, 73, 188, 173, 34, 27, 21, 147, 243, 196, 203, 155, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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