Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff762adf51f6e470c74962d5f5324281e85e6f16af13ac683c00d0e5ee2337a7

Tx prefix hash: 20f467697e93b930bbac09022416e2a0c3570ab5fece4a8f59bb5eb16339ef52
Tx public key: dcc4992ba74dd37a254326df2c053b0b49672e4f8af8b2163ce224d241a348ff
Timestamp: 1709404696 Timestamp [UCT]: 2024-03-02 18:38:16 Age [y:d:h:m:s]: 01:112:20:09:27
Block: 969726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341468 RingCT/type: yes/0
Extra: 01dcc4992ba74dd37a254326df2c053b0b49672e4f8af8b2163ce224d241a348ff02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dcb4387c7a122c710f16d54b34a7c31dc5bec977a897f049edf9734ca413f43 0.600000000000 1429565 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": 969736, "vin": [ { "gen": { "height": 969726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dcb4387c7a122c710f16d54b34a7c31dc5bec977a897f049edf9734ca413f43" } } ], "extra": [ 1, 220, 196, 153, 43, 167, 77, 211, 122, 37, 67, 38, 223, 44, 5, 59, 11, 73, 103, 46, 79, 138, 248, 178, 22, 60, 226, 36, 210, 65, 163, 72, 255, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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