Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2774d987287925c39ec5d4a6a611ac447b2dd5c6bd9bb6d5cd3cb6b38ce80f69

Tx prefix hash: db83121c564cdfd7d7f92479bccd029219b3445818dc9b9c84c89be50f68822f
Tx public key: fc1512a8857f2eec5ac366253f2ea4ba3fde67a1613df1f741bfd8c263b07eac
Timestamp: 1574659050 Timestamp [UCT]: 2019-11-25 05:17:30 Age [y:d:h:m:s]: 05:070:06:33:20
Block: 16934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192824 RingCT/type: yes/0
Extra: 01fc1512a8857f2eec5ac366253f2ea4ba3fde67a1613df1f741bfd8c263b07eac021100000001f95225a5000000000000000000

1 output(s) for total of 539.375865179000 dcy

stealth address amount amount idx
00: 6b357c7198f1d4b43674e0c3e3c736b399d43015bdf2c65d20a9430e0918f222 539.375865179000 24122 of 0

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": 16944, "vin": [ { "gen": { "height": 16934 } } ], "vout": [ { "amount": 539375865179, "target": { "key": "6b357c7198f1d4b43674e0c3e3c736b399d43015bdf2c65d20a9430e0918f222" } } ], "extra": [ 1, 252, 21, 18, 168, 133, 127, 46, 236, 90, 195, 102, 37, 63, 46, 164, 186, 63, 222, 103, 161, 97, 61, 241, 247, 65, 191, 216, 194, 99, 176, 126, 172, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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