Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1bc8f8daca7eb3918620a107a14e57e00558a9d4f23cb6433a0f6dc61115651

Tx prefix hash: ec8e5d7614c919b9456202ebae2a090785094abd5ddddbdd49791c1725e235f0
Tx public key: ab9c2dcd0aa5026a761180447b4d9c2e764fc165b36f6cc1422aa3d1a12ac676
Timestamp: 1707776431 Timestamp [UCT]: 2024-02-12 22:20:31 Age [y:d:h:m:s]: 01:262:00:15:28
Block: 956211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446019 RingCT/type: yes/0
Extra: 01ab9c2dcd0aa5026a761180447b4d9c2e764fc165b36f6cc1422aa3d1a12ac6760211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ced425b4d01c2270ecac3eafa8af8d77a78385c300508f77048b64e1acd374 0.600000000000 1415515 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": 956221, "vin": [ { "gen": { "height": 956211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ced425b4d01c2270ecac3eafa8af8d77a78385c300508f77048b64e1acd374" } } ], "extra": [ 1, 171, 156, 45, 205, 10, 165, 2, 106, 118, 17, 128, 68, 123, 77, 156, 46, 118, 79, 193, 101, 179, 111, 108, 193, 66, 42, 163, 209, 161, 42, 198, 118, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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