Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4687b82f190fa2962063fba3e630d07a5567cbed9222f0451390dd761d890278

Tx prefix hash: 9a9684ffa34e9e6a7a3eabe6ab62db23fd70a2e198ce326000eb78eee67a5d9b
Tx public key: 318a444f875e096c21d84a580b4194769fcfeccb17d8e3d6b82b4e20b010f21c
Timestamp: 1704837849 Timestamp [UCT]: 2024-01-09 22:04:09 Age [y:d:h:m:s]: 01:116:05:26:55
Block: 931839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344188 RingCT/type: yes/0
Extra: 01318a444f875e096c21d84a580b4194769fcfeccb17d8e3d6b82b4e20b010f21c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9eb0e95cea3185d9f3c20127ce596c91f1d03573a05986df6a8c813a88f14ba 0.600000000000 1389743 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": 931849, "vin": [ { "gen": { "height": 931839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9eb0e95cea3185d9f3c20127ce596c91f1d03573a05986df6a8c813a88f14ba" } } ], "extra": [ 1, 49, 138, 68, 79, 135, 94, 9, 108, 33, 216, 74, 88, 11, 65, 148, 118, 159, 207, 236, 203, 23, 216, 227, 214, 184, 43, 78, 32, 176, 16, 242, 28, 2, 17, 0, 0, 0, 1, 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