Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f5f659a1c6625d27c7bc00b850a18778e561cf7e4206c6f9296b206072fac14

Tx prefix hash: 965558a66a62669fd35011a89b1b9fbc3b35db39430482415dd34c37dd617b85
Tx public key: f286eb37a7d01e6d8736d7f2564a6aff77e540a4125719527d99645b5e4acb17
Timestamp: 1729919482 Timestamp [UCT]: 2024-10-26 05:11:22 Age [y:d:h:m:s]: 00:087:18:51:53
Block: 1139766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62715 RingCT/type: yes/0
Extra: 01f286eb37a7d01e6d8736d7f2564a6aff77e540a4125719527d99645b5e4acb17021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a27b3329d4da7e22ab37e69f2ff49260185083f1e523f02bf7ddb61bb2fbf74e 0.600000000000 1623553 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": 1139776, "vin": [ { "gen": { "height": 1139766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a27b3329d4da7e22ab37e69f2ff49260185083f1e523f02bf7ddb61bb2fbf74e" } } ], "extra": [ 1, 242, 134, 235, 55, 167, 208, 30, 109, 135, 54, 215, 242, 86, 74, 106, 255, 119, 229, 64, 164, 18, 87, 25, 82, 125, 153, 100, 91, 94, 74, 203, 23, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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