Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61dbb128b5ec85b58720c9b5f9cb763a838ddf929931887a8c2a4ac03aefaf79

Tx prefix hash: 0f5bd88b4c275043a5381d25019023c628ad9578751f5df43a0a6b66fe2af447
Tx public key: 7db35320f33fd1321c0d4930f916a32fa53f39220515e1798992f17ca9b9d487
Timestamp: 1582944922 Timestamp [UCT]: 2020-02-29 02:55:22 Age [y:d:h:m:s]: 04:338:18:02:28
Block: 73746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135571 RingCT/type: yes/0
Extra: 017db35320f33fd1321c0d4930f916a32fa53f39220515e1798992f17ca9b9d487021100000011c71d3ff9000000000000000000

1 output(s) for total of 349.663006705000 dcy

stealth address amount amount idx
00: 41c7076a88f98e4d627233c20d0a1fa212d19a5d553b281f84379f389ae658ca 349.663006705000 136123 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": 73756, "vin": [ { "gen": { "height": 73746 } } ], "vout": [ { "amount": 349663006705, "target": { "key": "41c7076a88f98e4d627233c20d0a1fa212d19a5d553b281f84379f389ae658ca" } } ], "extra": [ 1, 125, 179, 83, 32, 243, 63, 209, 50, 28, 13, 73, 48, 249, 22, 163, 47, 165, 63, 57, 34, 5, 21, 225, 121, 137, 146, 241, 124, 169, 185, 212, 135, 2, 17, 0, 0, 0, 17, 199, 29, 63, 249, 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