Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a17d8924656c0ea0e1c4a7dd6b51e9a095ac6f2f3f0e2fc3270997335c1c5fd

Tx prefix hash: 676fde67a28f3486c4f26363144050e4fb350d18c20b5630aa8001816e4ee13c
Tx public key: 238b77bf3ebcc5d914016947da502ef70af2dc166e548dcb9a0e82b657b6df45
Timestamp: 1715644708 Timestamp [UCT]: 2024-05-13 23:58:28 Age [y:d:h:m:s]: 01:036:18:33:59
Block: 1021444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287091 RingCT/type: yes/0
Extra: 01238b77bf3ebcc5d914016947da502ef70af2dc166e548dcb9a0e82b657b6df450211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a747339b004644a024deaf704c070c92af4400fdac596f87c48a055a84c2379a 0.600000000000 1485765 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": 1021454, "vin": [ { "gen": { "height": 1021444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a747339b004644a024deaf704c070c92af4400fdac596f87c48a055a84c2379a" } } ], "extra": [ 1, 35, 139, 119, 191, 62, 188, 197, 217, 20, 1, 105, 71, 218, 80, 46, 247, 10, 242, 220, 22, 110, 84, 141, 203, 154, 14, 130, 182, 87, 182, 223, 69, 2, 17, 0, 0, 0, 1, 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