Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87ca89234be2bc3a71078d0ef03a892146754b2f2a7d7c37c00ee894d66baa4f

Tx prefix hash: 50b414ac4b7eeb40c179fbfd0c09e1836f79b095feeb15167517811796122bf4
Tx public key: a18c9430a773c70dd502588df14511e71fb0d4238a0bb09eac1d50e3b2602610
Timestamp: 1732037049 Timestamp [UCT]: 2024-11-19 17:24:09 Age [y:d:h:m:s]: 00:215:07:16:14
Block: 1157261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153533 RingCT/type: yes/0
Extra: 01a18c9430a773c70dd502588df14511e71fb0d4238a0bb09eac1d50e3b2602610021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76c228a7c2ab4ef4a467dcc64496f8e8137e914983bfda28b9feda1ea7f22f3a 0.600000000000 1642884 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": 1157271, "vin": [ { "gen": { "height": 1157261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76c228a7c2ab4ef4a467dcc64496f8e8137e914983bfda28b9feda1ea7f22f3a" } } ], "extra": [ 1, 161, 140, 148, 48, 167, 115, 199, 13, 213, 2, 88, 141, 241, 69, 17, 231, 31, 176, 212, 35, 138, 11, 176, 158, 172, 29, 80, 227, 178, 96, 38, 16, 2, 17, 0, 0, 0, 2, 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