Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42bcc3b788e59e861ca83f77f248ebb9d84675308d2c010edc5b3ac4d1ca4e5c

Tx prefix hash: 2b1cfd219f09e5ee69f863c07b0c9a342afa43758dcc6cdb0f805dd66b42de6f
Tx public key: b17b072da94f9242d5971055ecd76ce6eb68c516b3ec43da3da131ae81b211de
Timestamp: 1717843940 Timestamp [UCT]: 2024-06-08 10:52:20 Age [y:d:h:m:s]: 00:307:23:16:21
Block: 1039685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220091 RingCT/type: yes/0
Extra: 01b17b072da94f9242d5971055ecd76ce6eb68c516b3ec43da3da131ae81b211de0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e559e3e014e969724e9935f5c38b6b60a685c07b4eae78fc4775dacb2a8e33ba 0.600000000000 1508334 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": 1039695, "vin": [ { "gen": { "height": 1039685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e559e3e014e969724e9935f5c38b6b60a685c07b4eae78fc4775dacb2a8e33ba" } } ], "extra": [ 1, 177, 123, 7, 45, 169, 79, 146, 66, 213, 151, 16, 85, 236, 215, 108, 230, 235, 104, 197, 22, 179, 236, 67, 218, 61, 161, 49, 174, 129, 178, 17, 222, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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