Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e5f64d0d86d518832a2f7daf7eb03f3705b58a03dd93c8e6e646d79219179b

Tx prefix hash: 889b5d559a6e04f9f03bf94c4fbcd56f78de2aa8a7ff078305d7d7c957cf0ee1
Tx public key: 83a82e709cdd9f492e75f4cd310ac1b87f431f5189fc2a836b37ff001f3137a7
Timestamp: 1730793366 Timestamp [UCT]: 2024-11-05 07:56:06 Age [y:d:h:m:s]: 00:019:00:05:04
Block: 1146956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13596 RingCT/type: yes/0
Extra: 0183a82e709cdd9f492e75f4cd310ac1b87f431f5189fc2a836b37ff001f3137a7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ce3edaf205bc0680f0fc760f3e33d061cb568cb160a6c92b1b4d246ee9cd55 0.600000000000 1631649 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": 1146966, "vin": [ { "gen": { "height": 1146956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ce3edaf205bc0680f0fc760f3e33d061cb568cb160a6c92b1b4d246ee9cd55" } } ], "extra": [ 1, 131, 168, 46, 112, 156, 221, 159, 73, 46, 117, 244, 205, 49, 10, 193, 184, 127, 67, 31, 81, 137, 252, 42, 131, 107, 55, 255, 0, 31, 49, 55, 167, 2, 17, 0, 0, 0, 5, 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