Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbb2c83438c9bd843b00536f047a5b1a2f67096c19eadd5834891326cd12a744

Tx prefix hash: eae968f299abcb64cae69a8432d2110b6fbf23972cb56c27a6daa9d792153123
Tx public key: 98ea4ee9bf71694476b9cb6c517050e0f316c20330dbbaa0726ed5e07f4087cd
Timestamp: 1741699312 Timestamp [UCT]: 2025-03-11 13:21:52 Age [y:d:h:m:s]: 00:261:16:31:03
Block: 1237000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184772 RingCT/type: yes/0
Extra: 0198ea4ee9bf71694476b9cb6c517050e0f316c20330dbbaa0726ed5e07f4087cd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0229e1876f01267e7ce5c17012ab3ec22a67f11d6c9a22f7f9bea8df1633741 0.600000000000 1723955 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": 1237010, "vin": [ { "gen": { "height": 1237000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0229e1876f01267e7ce5c17012ab3ec22a67f11d6c9a22f7f9bea8df1633741" } } ], "extra": [ 1, 152, 234, 78, 233, 191, 113, 105, 68, 118, 185, 203, 108, 81, 112, 80, 224, 243, 22, 194, 3, 48, 219, 186, 160, 114, 110, 213, 224, 127, 64, 135, 205, 2, 17, 0, 0, 0, 4, 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