Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291448dbc3433070c01f1f17c833f879c4df578867f3f5db246b3ce6eaed51a8

Tx prefix hash: 06a069759d734c04f284535a27191b8803a7c367b8617f9ecfccdfd2407fa413
Tx public key: 36802cbcc1535d2a203d6e958c8b89a9005f389a3feb6bd6a54d871085e09139
Timestamp: 1702710353 Timestamp [UCT]: 2023-12-16 07:05:53 Age [y:d:h:m:s]: 01:036:06:02:53
Block: 914214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287218 RingCT/type: yes/0
Extra: 0136802cbcc1535d2a203d6e958c8b89a9005f389a3feb6bd6a54d871085e0913902110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeea25a03855e94ddcaecbf789ae19a03ffe4e06a3e8d56c9dadd31d7db99652 0.600000000000 1371500 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": 914224, "vin": [ { "gen": { "height": 914214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeea25a03855e94ddcaecbf789ae19a03ffe4e06a3e8d56c9dadd31d7db99652" } } ], "extra": [ 1, 54, 128, 44, 188, 193, 83, 93, 42, 32, 61, 110, 149, 140, 139, 137, 169, 0, 95, 56, 154, 63, 235, 107, 214, 165, 77, 135, 16, 133, 224, 145, 57, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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