Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bfa6d48662ee132b63a95683e2a6299f96b4e86a69533f59cdd2cc7b6f01d63

Tx prefix hash: 4ca1df661bbf8b81c67cf466a22af6900c3beb52b6082d97632beea9778d12dc
Tx public key: 85a25abf82dce0885bf18c519a6a7f198474bf4d440fd77fdc1f23da1b72cce2
Timestamp: 1746551204 Timestamp [UCT]: 2025-05-06 17:06:44 Age [y:d:h:m:s]: 00:198:08:37:02
Block: 1277157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139464 RingCT/type: yes/0
Extra: 0185a25abf82dce0885bf18c519a6a7f198474bf4d440fd77fdc1f23da1b72cce20211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 865b5c94191bda9743e0cf12a386366bd2dfb2ee2e58a2a978c1386278d6b232 0.600000000000 1764508 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": 1277167, "vin": [ { "gen": { "height": 1277157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "865b5c94191bda9743e0cf12a386366bd2dfb2ee2e58a2a978c1386278d6b232" } } ], "extra": [ 1, 133, 162, 90, 191, 130, 220, 224, 136, 91, 241, 140, 81, 154, 106, 127, 25, 132, 116, 191, 77, 68, 15, 215, 127, 220, 31, 35, 218, 27, 114, 204, 226, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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