Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a30a1a175f9f17a4113ec205d758dd883c18e3cb51a6350f38530fdc5236fb1

Tx prefix hash: 63c00287016c022f349a7ae33c4b87b13b7ac738ebca8b2c46eecc55a8ed36b2
Tx public key: c1c281bbc6a228a918fa1ddf4e2b73f48032e18dc8c352874359a913b41127bb
Timestamp: 1744055897 Timestamp [UCT]: 2025-04-07 19:58:17 Age [y:d:h:m:s]: 00:227:13:01:21
Block: 1256479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160354 RingCT/type: yes/0
Extra: 01c1c281bbc6a228a918fa1ddf4e2b73f48032e18dc8c352874359a913b41127bb02110000000adbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8173baad40d0b5d0e2802bd977c3f60254c9ccbb7c957ab09fdb4ff1024bd28 0.600000000000 1743592 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": 1256489, "vin": [ { "gen": { "height": 1256479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8173baad40d0b5d0e2802bd977c3f60254c9ccbb7c957ab09fdb4ff1024bd28" } } ], "extra": [ 1, 193, 194, 129, 187, 198, 162, 40, 169, 24, 250, 29, 223, 78, 43, 115, 244, 128, 50, 225, 141, 200, 195, 82, 135, 67, 89, 169, 19, 180, 17, 39, 187, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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